home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
qbbs
/
q2day220.zip
/
QBBS2DAY.DOC
< prev
next >
Wrap
Text File
|
1990-05-14
|
19KB
|
488 lines
════════════════════════════════════════════════════
QBBS2DAY
════════════════════════════════════════════════════
Version 2.20
05/14/90
The Mailer / BBS System-Usage-Graph Generator
for
QuickBBS
Remote Access
OPUS
by
Robert Hermans
Copyright (C) 1989-1990 Robert Hermans. All rights reserved.
WHAT IS QBBS2DAY ?
────────────────────
QBBS2DAY is a professional BBS System - Usage - Graph generator,
just like QuickBBS/RA owns System-usage-graph (menu-type 10), but it is a
lot BETTER, MORE ATTRACTIVE and can do MUCH MORE! QBBS2DAY can be used
for QuickBBS, RemoteAccess and OPUS. It combines the internal system-usage
with those from FrontDoor or Binkley (Mailers), so you and your users get a
"real" idea of what's going on in your BBS.
QBBS2DAY started it's way in december of 1989 as an exact clone of QBS
by ...... and it is written using Borland's TURBO Pascal 5.5.
DISCLAIMER, LICENSE AND OTHER IMPORTANT STUFF
─────────────────────────────────────────────
The following points must be considered, understood and agreed upon
BEFORE you use QBBS2DAY:
* QBBS2DAY is ShareWare, and not FreeWare or Public Domain !
* This documentation and the accompanying program is copyrighted material
by Robert Hermans.
* Although care has been taken to write and test a program that does what
this documentation states, the program is provided as it is, without
warranty or guarantee of any kind, either expressed or implied, as to
the quality or performance of this program, except that it will occupy
disk space.
* You may not make any changes or modifications to the program and you may
not de-compile, disassemble, or otherwise reverse-engineer it. You may
not rent or lease it to others.
* The author will not be held liable to you or anyone for any direct,
indirect, incidental, consequential or other similar damages, including
any lost profits, lost savings which may result from the use or inability
to use this program. Your use of the program constitutes your agreement
to this disclaimer and your release of the author from any form of
liability or litigation.
* I grant you a limited license to use QBBS2DAY and encourage you to copy
and distribute it in an unmodified way as much as you want, as long as
you still abide to the conditions mentioned here and no money or other
compensation is asked or accepted.
INSTALLATION & CONFIGURATION
────────────────────────────
QuickBBS, Remote Access
* Put QBBS2DAY.EXE somewhere on your hard disk.
* Enter your info and wishes in the control file QBBS2DAY.CTL. You won't
have much trouble with this. Make sure that QBBS2DAY can find that file
in the current directory when it is started.
* Put QBBS2DAY in your batch file to run it in your daily event or after
each user. Keep in mind that you have to start QBBS2DAY from the path
where QuickBBS system files are placed to ensure QBBS2DAY finds
QuickBBS's CONFIG.BBS and TIMELOG.BBS (RA users have to start QBBS2DAY
in RA's system path).
* Now you have to change the option in your menu for the system usage graph,
from menu type 10 to 45 (or 5), and too place the following on the
optional data-line: QDAY
* Registered users can also show their bbs-users a system usage graph
of the FrontDoor/Binkley activity. To do so you just have to place a
additional line in your menu with type 45 (or 5) and a data-line
saying: QDAYMAIL
QBBS2DAY will create the reports in your text files path (which is
obtained from the CONFIG file). QBBS2DAY will put a Ctrl-L (Screen
Clearing Codes) in the beginning of the file. You can display these
files to your users by using QuickBBS (RA) TYPE 5 or TYPE 45
("Press [ENTER] to continue:" ) commands.
QBBS2DAY will create two files named QDAY.ASC and QDAY.ANS. A file
called QBBS2DAY.DAT will be created by enabling FrontDoor/Binkley activity.
This file stores all information needed to process a FrontDoor/Binkley
activity chart.
It must be started everytime a user log's on (or off) so the system-
usage-graph will be up too date. You may also run QBBS2DAY in a event if
you like, but then the system-usage-graph will not be so up too date as
running QBBS2DAY everytime a user logs on (or off). Watch out, running
QBBS2DAY when a user logs ON will cause him/her to wait a while.
I suggest running QBBS2DAY after a user logs off and everytime a mailer
called if FrontDoor/Binkley activity is enabled.
INSTALLATION & CONFIGURATION
────────────────────────────
OPUS
* Put QBBS2DAY.EXE somewhere on your hard disk.
* Enter your info and wishes in the control file QBBS2DAY.CTL. You won't
have much trouble with this. Make sure that QBBS2DAY can find that file
in the current directory when it is started.
* Put QBBS2DAY in your batch file to run it in your daily event or after
each user. QBBS2DAY generates a file called QBBS2DAY.OPS, all activity
of OPUS will be stored in this file (at this time these data will be
taken out of Binkleys logfile, but has to be defined seperately).
* You can display these files to your users by using its typical
OPUS command "<CTRL-O>SQDAY".
* Registered users can also show their bbs-users a system usage graph
of the FrontDoor/Binkley activity. To do so you just have to place a
additional line in your file saying: <CTRL-O>SQDAYMAIL
QBBS2DAY will create the reports in your text files path (which is obtained
from the CONFIG file). QBBS2DAY will put a Ctrl-L (Screen Clearing Codes) in
the beginning of the file.
QBBS2DAY will create two files named QDAY.BBS and QDAY.GBS. A file
called QBBS2DAY.DAT will be created by enabling FrontDoor/Binkley activity.
This file stores all information needed to process a FrontDoor/Binkley
activity chart.
It must be started everytime a user log's on (or off) so the system-
usage-graph will be up too date. You may also run QBBS2DAY in a event if
you like, but then the system-usage-graph will not be so up too date as
running QBBS2DAY everytime a user logs on (or off). Watch out, running
QBBS2DAY when a user logs ON will cause him/her to wait a while.
I suggest running QBBS2DAY after a user logs off and everytime a mailer
called if FrontDoor/Binkley activity is enabled.
Note:
QBBS2DAY reads all lines starting with # and *.
The exact online-time is calculated from two lines in your log-file:
# dd mmm hh:mm:ss BINK Connect ..... / start of session
line w/o OPUS after dd mmm hh:mm:ss / end of session
You can change these lines by inserting the follwing code into the
configuration file:
OPUS-START char <- Default-char: #
OPUS-STARTTEXT text <- Default-text: BINK Connect
OPUS-ENDTEXT text <- Default-text: OPUS
Note: If you have another date/time format please contact me, so
i can change my program to fit to your logfile-format.
CONFIGURATION FILE
──────────────────
You'll have to create a file named QBBS2DAY.CTL if you want one or more
of the following things:
* define your BBS-system (QuickBBS, RAccess, OPUS)
* different colors (ANSI)
* defineable character (registration requiered)
* IBM-ASCII (8-bit ascii-characters)
* IBM-ANSI (8-bit ascii-characters)
* own messages (native language, etc.)
* Mailer activity included (FrontDoor, Binkley, D'Bridge)
You can place any of these commands into QBBS2DAY.CTL:
Mandatory:
BBSSYSTEM system <- define BBS system (RA, QBBS or OPUS)
TEXTPATH path <- path, where to place the ASC/ANS (BBS/GBS) files
this command must be used with OPUS and can be
used with QBBS/RA if you don't want QBBS2DAY too
use the data in the BBS-configurationfile. If no
BBS-configurationfile is found and no TEXTPATH
added to QBBS2DAY.CTL the execution of this
programm is aborted.
Optional:
HIGH ansi-code <- title color
NORM ansi-code <- border colors
MAILER ansi-code <- chart colors for mailers
CALLER ansi-code <- chart colors for human callers
HEADER text ^F text <- define own header (max. 79 characters)
AVG text <- define average text (max. 4 characters)
DEFINE text <- enable definition text (max. 70 characters)
(explaination about mailer, caller)
IBM-DEFINE text <- enable definition text ibm-charset
(explaination about mailer, caller)
IBM-ASCII <- enable IBM-ASCII codes in ASCII file
IBM-ANSI <- enable IBM-ASCII codes in ANSI file
Opus:
OPUS-COMMAND text <- enable execution of OPUS-command at end of
BBS/GBS files (OPUS only)
OPUS-LOGPATH path <- path and name of OPUS logfile
Mailer:
MAIL <- include Mailer activity
MAILERSYSTEM system <- define mailer, FrontDoor (F), Binkley (B) or
D'Bridge (D)
MAILLOG path <- path and name of mailer-logfile
MAILHEADER text ^F text <- define own header for mailer-activity chart
Notes: ansi-code == textstring with ansi codes, up to 10 characters
It's a good idea to have the same backgroundcolors
for mailer and caller.
text == string with ascii characters and NO ansi-codes.
^F will represent the number of days which are
included in the activity chart.
CONFIGURATION FILE (Registered QBBS2DAY)
────────────────────────────────────────
You can add these following lines to the configuration file:
Mailer:
MAILCHART <- create extra chart for Mailer Activity
these files will be called QDAYMAIL.ANS/ASC
MAILCHAR <- let's QBBS2DAY use callers-characters in
QDAYMAIL ansi file.
IBM-characters:
IBM-CharCLo char (▄) <- define caller half size
IBM-CharCHi char (█) <- define caller full size
IBM-CharCALo char (▄) <- define caller half size middle avg.
IBM-CharCAHi char (█) <- define caller full size middle avg.
IBM-CharMLo char (╥) <- define mailer half size
IBM-CharMHi char (║) <- define mailer full size
IBM-CharMALo char (╥) <- define mailer half size middle avg.
IBM-CharMAHi char (╫) <- define mailer full size middle avg.
IBM-CharAVG char (») <- define middle average sign
IBM-CharMDL char (─) <- define middle average (line)
Standard-ASCII-characters:
ASC-CharCLo char (c) <- Define caller half size
ASC-CharCHi char (C) <- define caller full size
ASC-CharMLo char (m) <- define Mailer half size
ASC-CharMHi char (M) <- define mailer full size
ASC-CharAVG char (>) <- define middle average sign
ASC-CharMDL char (-) <- define middle average (line)
CONFIGURATION - FrontDoor
───────────────────────────
FrontDoor:
If you're including FrontDoor activity please have the following
four lines:
" * Sent/Rcvd files "
" ~ Session information "
" - Trivial messages "
" + Brief messages "
set to Y E S in FrontDoor-Setup Mailer / Miscellaneous / Log.
CONFIGURATION - Binkley
─────────────────────────
Binkley:
QBBS2DAY reads all lines starting with # and *.
The exact online-time is calculated from two lines in your log-file:
# dd mmm hh:mm:ss BINK Connect ..... / start of session
* dd mmm hh:mm:ss BINK End ...... / end of session
You can change these lines by inserting the follwing code into the
configuration file:
BINK-START char <- Default-char: #
BINK-STARTTEXT text <- Default-text: BINK Connect
BINK-END char <- Default-char: *
BINK-ENDTEXT text <- Default-text: BINK End
Note: If you have another date/time format please contact me, so
i can change my program to fit to your logfile-format.
CONFIGURATION - D'Bridge
──────────────────────────
D'Bridge:
The online-time is calculated from these lines in your log-file:
mm/dd/yy hh:mm EMSI: ..... / start of session
mm/dd/yy hh:mm YOOHOO: ..... / start of session
mm/dd/yy hh:mm Mail sent successfully ...... / end of session
mm/dd/yy hh:mm One connection ...... / end of session
mm/dd/yy hh:mm Bad/incomplete archive ...... / end of session
You can change these lines by inserting the following code into the
configuration file:
DB-STARTTEXT text <- Default-text: EMSI:
DB-STARTTEXT1 text <- Default-text: YOOHOO:
DB-ENDTEXT text <- Default-text: SESSION SUCCESSFUL
DB-ENDTEXT2 text <- Default-text: ONE PACKET
DB-ENDTEXT3 text <- Default-text: BAD/INCOMPLETE ARCHIVE
CONFIGURATION - D'Bridge 1.31 and higher
──────────────────────────────────────────
D'Bridge:
The online-time should be calculated from these lines in your log-file:
mm/dd/yy hh:mm EMSI: ..... / start of session
mm/dd/yy hh:mm YOOHOO: ..... / start of session
mm/dd/yy hh:mm Inbound session complete ...... / end of session
mm/dd/yy hh:mm Estimation ...... / end of session
mm/dd/yy hh:mm Session failure ...... / end of session
You can change these lines by inserting the following code into the
configuration file:
DB-STARTTEXT text <- Default-text: EMSI:
DB-STARTTEXT1 text <- Default-text: YOOHOO:
DB-ENDTEXT text <- Recommended: INBOUND SESSION COMPLETE
DB-ENDTEXT2 text <- Recommended: ESTIMATION
DB-ENDTEXT3 text <- Recommended: SESSION FAILURE
Note: If you have another date/time format please contact me, so
i can change my program to fit to your logfile-format.
RELEASES
────────
v1.00 full release
QuickBBS chart generated as a copy of QBS
v2.00 full release
QuickBBS,RA and FrontDoor are supported, seperate chart for
registered user implemented.
v2.10 full release
BINKLEY is supported. Changes all Mailernames from FD to MAIL
OPUS is supported (beta-test). QuickBBS / RA configurationfile
can be ignored by adding TEXTPATH to controlfile.
bug in day-lap fixed, no more 1440minutes if mailer logged in
at 23.00hrs and leaves at 0.00hrs.
v2.11 beta-test
bug in daycount fixed, so Timelog.BBS may be older than a year.
v2.12 beta-test
implemented D'Bridge v1.18 mailer-activity.
v2.13 beta-test
appended ANSI-reset-command to end of chart. (ESC [0m)
implemented D'Bridge v1.30 mailer-activity.
v2.20 full release
update to D'Bridge v1.31, 2 START and 3 END commands
are recognized. QBBS2DAY tested with LZEXE and NO problems
were found.
HISTORY / FUTURE:
─────────────────
Until now I spent hours thinking, writing, converting, debugging and
documenting QBBS2DAY, and I will keep on doing that. QBBS2DAY is a little
bit crippled: if you don't register, it will not display a extra file
showing FrontDoor/Binkley's Mailer-activity (QDAYMAIL.A??). If you use this
program for a period of time and you decide you like it, you can get a
registration *) key by sending the EXACT TEXT you want QBBS2DAY registered
too and which version you are currently using, along with any questions,
comments, suggestions and bug-reports, and of course your (net) mail address,
to:
Robert Hermans
Hoosveld 35
NL - 6075 DC Herkenbosch
The Netherlands
If you run into any bugs or problems you cannot solve, I can be reached
either through my BBS, too:
DC SKYline
(FidoNet 2:512/102)
INTL-31-4752-5306
(V.21, V.22, V.22bis, V.32, HST 14400)
*) REGISTRATION
────────────
There are two ways of registration :
1.) By using QBBS2DAY on a regulary basis you MUST SEND a POSTCARD to my
home address (shown above). All I ask is to be able to show your postcard
to my grandchildren and say "Look at this one Becky - here's another nice
postcard from a guy at Lake Powell, Arizona".
2.) A contribution of at least US$ 10.00, sent to the above address, would
be greatly appreciated. Dutch residents may send guildes instead.
Note: If you're using money-registration you'll receive your key thru
netmail, if your nodenumber is present, otherwise you'll have to poll
DC SKYline (2:512/102) to get the desired key. If you're using
Postcard-registration you allways have to poll to receive your key.
Please allow up to 21 days too process due to Post-transportation speed.
OFFICIAL QBBS2DAY BETA & DISTRIBUTION SITES:
────────────────────────────────────────────
Node Sysop BBS Name Phone
══════════════════════════════════════════════════════════════════════
2:512/102 Robert Hermans DC SKYline 31-4752-5306 V32, HST
2:242/5 Uwe Muckel Mail-Power 49-2456-3723 HST
You can always request the latest version here, using alias "QBBS2DAY".
I would like to thank my beta testers/support nodes for their help with this
and many other projects. I couldn't have done it without them!